Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 989cce30bd3863ac042259ccd6bce49e65628cc39de55dd34be0dee71a3f1f29

Tx prefix hash: 49670fc50f1e02828a0f5795de80868e37635c7bac3e4373d1eb3378d4fac56f
Tx public key: 650028a6e0fc3e5c17cd02f3f7d0879f188ac6c8b897288af57d764b22f878ae
Timestamp: 1640548415 Timestamp [UTC]: 2021-12-26 19:53:35 Age [y:d:h:m:s]: 04:136:02:45:52
Block: 404076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1127321 RingCT/type: yes/0
Extra: 01650028a6e0fc3e5c17cd02f3f7d0879f188ac6c8b897288af57d764b22f878ae021100000002a272b9cb000000000000000000

1 output(s) for total of 0.028127350013 xmr

stealth address amount amount idx tag
00: a82dc5b86fc90c72c0f9d996fac3fb344edfb1a5dd7a6b3ee45a97a8de40b4d2 0.028127350013 804079 of 0 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 404086, "vin": [ { "gen": { "height": 404076 } } ], "vout": [ { "amount": 28127350013, "target": { "key": "a82dc5b86fc90c72c0f9d996fac3fb344edfb1a5dd7a6b3ee45a97a8de40b4d2" } } ], "extra": [ 1, 101, 0, 40, 166, 224, 252, 62, 92, 23, 205, 2, 243, 247, 208, 135, 159, 24, 138, 198, 200, 184, 151, 40, 138, 245, 125, 118, 75, 34, 248, 120, 174, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: