Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94e6904fc6c3f8c69661327841e5eade87053e752a88d3f698fc019716aeebbb

Tx prefix hash: 4dab608fecca4f41b91ed23cb3199cc0b7ce50bbba67b07eab5f092685cd7f5b
Tx public key: f950f66d08ef63563f35649bd040c2a8bce11d3e97f39faafb8c76b0b66ed9e0
Timestamp: 1721884098 Timestamp [UCT]: 2024-07-25 05:08:18 Age [y:d:h:m:s]: 00:277:07:51:24
Block: 1073167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198148 RingCT/type: yes/0
Extra: 01f950f66d08ef63563f35649bd040c2a8bce11d3e97f39faafb8c76b0b66ed9e0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0162f4fa4e4e0daa02d821cbe129a4dbbe737f5e29a6e87360b824e754f7d1 0.600000000000 1545666 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": 1073177, "vin": [ { "gen": { "height": 1073167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0162f4fa4e4e0daa02d821cbe129a4dbbe737f5e29a6e87360b824e754f7d1" } } ], "extra": [ 1, 249, 80, 246, 109, 8, 239, 99, 86, 63, 53, 100, 155, 208, 64, 194, 168, 188, 225, 29, 62, 151, 243, 159, 170, 251, 140, 118, 176, 182, 110, 217, 224, 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