Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406f2f23daed2dcd03dc641331c4035c31367f9a84b9185ae393705107260a7b

Tx prefix hash: 0cc4578e8b785a7b1820432b7bdd3d624c67161ce7876f92fe90279d8702600f
Tx public key: 97f94cf058dbc61c0e3e425354d917563b3b6d2715af156a51e9df23118e80d8
Timestamp: 1721866838 Timestamp [UCT]: 2024-07-25 00:20:38 Age [y:d:h:m:s]: 00:275:02:40:08
Block: 1073032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196542 RingCT/type: yes/0
Extra: 0197f94cf058dbc61c0e3e425354d917563b3b6d2715af156a51e9df23118e80d802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d78e39a49be16f7aa40cac59fb9254f8c74ebc6b4855a1baea46258efdd6996 0.600000000000 1545531 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": 1073042, "vin": [ { "gen": { "height": 1073032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d78e39a49be16f7aa40cac59fb9254f8c74ebc6b4855a1baea46258efdd6996" } } ], "extra": [ 1, 151, 249, 76, 240, 88, 219, 198, 28, 14, 62, 66, 83, 84, 217, 23, 86, 59, 59, 109, 39, 21, 175, 21, 106, 81, 233, 223, 35, 17, 142, 128, 216, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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