Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41df5c10a2f90fc64a9c33d1e5d379031ba9736fcc3cf2a3937d87b1b86a22a0

Tx prefix hash: 405dd548680fa547d4bdc56489172e8781b5ea5c8f475ba9a777b9e588b13d1f
Tx public key: dcac130309a3df48224f1f2d4c946184e9d16a0fcae9acc9e8daaac593d40eb5
Timestamp: 1722021131 Timestamp [UCT]: 2024-07-26 19:12:11 Age [y:d:h:m:s]: 01:149:22:45:33
Block: 1074309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365724 RingCT/type: yes/0
Extra: 01dcac130309a3df48224f1f2d4c946184e9d16a0fcae9acc9e8daaac593d40eb5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a81ba1aa0a7a6fa0b7ce61a5002abcee18dd7ac6194967175d75229f131ba7 0.600000000000 1546822 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": 1074319, "vin": [ { "gen": { "height": 1074309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a81ba1aa0a7a6fa0b7ce61a5002abcee18dd7ac6194967175d75229f131ba7" } } ], "extra": [ 1, 220, 172, 19, 3, 9, 163, 223, 72, 34, 79, 31, 45, 76, 148, 97, 132, 233, 209, 106, 15, 202, 233, 172, 201, 232, 218, 170, 197, 147, 212, 14, 181, 2, 17, 0, 0, 0, 5, 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