Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bad4bdc44809effe21d84ffe65358fc87d1bdb1c93d4d0ef953382533b80a06f

Tx prefix hash: 4a579d203534bdd05b5a2e3f35c45e76fbd557dc8cc6bdde841e3a283f6f1025
Tx public key: 94fc0fe04a0293638ff4039e41b3df7bb72cc5931b4cfef309dbe7e7e8a2f907
Timestamp: 1702606611 Timestamp [UCT]: 2023-12-15 02:16:51 Age [y:d:h:m:s]: 01:334:10:08:40
Block: 913348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497878 RingCT/type: yes/0
Extra: 0194fc0fe04a0293638ff4039e41b3df7bb72cc5931b4cfef309dbe7e7e8a2f907021100000009faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92378512a1d5295d9285a288e4bde5e575ca08bbf6e421f52147d06e885e0011 0.600000000000 1370616 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": 913358, "vin": [ { "gen": { "height": 913348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92378512a1d5295d9285a288e4bde5e575ca08bbf6e421f52147d06e885e0011" } } ], "extra": [ 1, 148, 252, 15, 224, 74, 2, 147, 99, 143, 244, 3, 158, 65, 179, 223, 123, 183, 44, 197, 147, 27, 76, 254, 243, 9, 219, 231, 231, 232, 162, 249, 7, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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