Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37d08de2b03fd785755791c3cb733595b0ae0d6b48731455909cb31c0132fd11

Tx prefix hash: 49c5c4d7dcb1ec8cca2e2e399dd8d247b981dcd89bda35a566d76a0a2d8814b2
Tx public key: fea6422c43c8578fe577291ef175ffdf7da12b0ff45a8e8829ab2afca7d8ab3f
Timestamp: 1725559326 Timestamp [UCT]: 2024-09-05 18:02:06 Age [y:d:h:m:s]: 00:265:15:25:14
Block: 1103654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189744 RingCT/type: yes/0
Extra: 01fea6422c43c8578fe577291ef175ffdf7da12b0ff45a8e8829ab2afca7d8ab3f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 743c52349cfe2d0fee478ebdc1818c09858dd27a456dbb0fbdb5ab4469241a86 0.600000000000 1580567 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": 1103664, "vin": [ { "gen": { "height": 1103654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "743c52349cfe2d0fee478ebdc1818c09858dd27a456dbb0fbdb5ab4469241a86" } } ], "extra": [ 1, 254, 166, 66, 44, 67, 200, 87, 143, 229, 119, 41, 30, 241, 117, 255, 223, 125, 161, 43, 15, 244, 90, 142, 136, 41, 171, 42, 252, 167, 216, 171, 63, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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