Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6a09b9dd0309a68c53e5f888d0cd3180c7e7d3cd57e1c11cf7006dd1ec2c66

Tx prefix hash: 3ebd38ffcbae75fb33903a77cfbc5c313ea0bec6b3aa59a47841c9a31117e95e
Tx public key: 8a2dc6aaf76f01c4ebf266dce00eebde3ba1eac345adedf5f226426601efa62e
Timestamp: 1579880943 Timestamp [UTC]: 2020-01-24 15:49:03 Age [y:d:h:m:s]: 06:303:15:56:01
Block: 52070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1631424 RingCT/type: yes/0
Extra: 018a2dc6aaf76f01c4ebf266dce00eebde3ba1eac345adedf5f226426601efa62e02110000000117786bcf000000000000000000

1 output(s) for total of 0.412544977945 xmr

stealth address amount amount idx tag
00: a0351684e824dc6c08f6196889eee7a16d769b4af3e1fbe0f23b155d1cb30945 0.412544977945 96443 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": 52080, "vin": [ { "gen": { "height": 52070 } } ], "vout": [ { "amount": 412544977945, "target": { "key": "a0351684e824dc6c08f6196889eee7a16d769b4af3e1fbe0f23b155d1cb30945" } } ], "extra": [ 1, 138, 45, 198, 170, 247, 111, 1, 196, 235, 242, 102, 220, 224, 14, 235, 222, 59, 161, 234, 195, 69, 173, 237, 245, 242, 38, 66, 102, 1, 239, 166, 46, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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: