Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c200c3d67a29eaa7bb987f2faeb08a2cfbc72828374bf9c4016a987f52a8e57d

Tx prefix hash: cc29afe89a2fd9c811835be6cffcc035a805636db37032bfd54ee7b3a6d03b8b
Tx public key: 0d30feb4bca98c32bd3ff534a474aa4001f2ae4de76175addd6f3c56199fc7f2
Timestamp: 1733741513 Timestamp [UCT]: 2024-12-09 10:51:53 Age [y:d:h:m:s]: 00:104:15:05:05
Block: 1171378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74553 RingCT/type: yes/0
Extra: 010d30feb4bca98c32bd3ff534a474aa4001f2ae4de76175addd6f3c56199fc7f20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0507ba98e36b79f57721d7caf6d50321380ed9790daf4c817aef1a875929a08 0.600000000000 1657125 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 dinasty-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": 1171388, "vin": [ { "gen": { "height": 1171378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0507ba98e36b79f57721d7caf6d50321380ed9790daf4c817aef1a875929a08" } } ], "extra": [ 1, 13, 48, 254, 180, 188, 169, 140, 50, 189, 63, 245, 52, 164, 116, 170, 64, 1, 242, 174, 77, 231, 97, 117, 173, 221, 111, 60, 86, 25, 159, 199, 242, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8