Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df4cc876c8221bf47d5ce5a312ca68b4b6afe39c5eebb441321d20497c2a7d4

Tx prefix hash: dd84774e042a63f057ab58aa941fd2d50cc2e84c4b5c711fa521a8ebd142919b
Tx public key: 993305d81a92a930cedd97e98fcc3800031fe262482fc7ef806fc40ee31fe5fb
Timestamp: 1702989414 Timestamp [UTC]: 2023-12-19 12:36:54 Age [y:d:h:m:s]: 02:332:03:16:13
Block: 916536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762464 RingCT/type: yes/0
Extra: 01993305d81a92a930cedd97e98fcc3800031fe262482fc7ef806fc40ee31fe5fb021100000001c5452960000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 827038bbb5e3d1b4588e716a24957841617bbaf46096638e6e73e64513c04fd0 0.000600000000 1374088 of 15 -

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": 916546, "vin": [ { "gen": { "height": 916536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "827038bbb5e3d1b4588e716a24957841617bbaf46096638e6e73e64513c04fd0" } } ], "extra": [ 1, 153, 51, 5, 216, 26, 146, 169, 48, 206, 221, 151, 233, 143, 204, 56, 0, 3, 31, 226, 98, 72, 47, 199, 239, 128, 111, 196, 14, 227, 31, 229, 251, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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: