Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc33aeedfe1cc7c51b226a2f4cdcda9867d4594a81d2ef86f31166c5df0b37d3

Tx prefix hash: 1c54dfe527a3987f089f44ca6861341620ad09c6729ec032c266b4710957513e
Tx public key: e858be522d12ff36eced4a953a95bea8c03a4715ab2ba3475fb1478a2c72d750
Timestamp: 1728393141 Timestamp [UCT]: 2024-10-08 13:12:21 Age [y:d:h:m:s]: 00:199:16:56:08
Block: 1127143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142527 RingCT/type: yes/0
Extra: 01e858be522d12ff36eced4a953a95bea8c03a4715ab2ba3475fb1478a2c72d750021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ce1b66674a7a6c2b93d6734a687e670be2cbb829ad880834512165ecec9fce1 0.600000000000 1609942 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": 1127153, "vin": [ { "gen": { "height": 1127143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ce1b66674a7a6c2b93d6734a687e670be2cbb829ad880834512165ecec9fce1" } } ], "extra": [ 1, 232, 88, 190, 82, 45, 18, 255, 54, 236, 237, 74, 149, 58, 149, 190, 168, 192, 58, 71, 21, 171, 43, 163, 71, 95, 177, 71, 138, 44, 114, 215, 80, 2, 17, 0, 0, 0, 1, 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