Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620b3d8053bd377bed670099f7d9d70843661d0d7e37c2ac6185c090bb7f889e

Tx prefix hash: 67c34739b48861eed6e23a1e6b4836fc3dd9e0bc7490a2e93b3f3ec6d6950b79
Tx public key: ca0e7ad81526ba18377ad292e84ebfb08537ef3b2c515d14c6640356e47fb909
Timestamp: 1715365496 Timestamp [UCT]: 2024-05-10 18:24:56 Age [y:d:h:m:s]: 00:334:14:47:21
Block: 1019139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239176 RingCT/type: yes/0
Extra: 01ca0e7ad81526ba18377ad292e84ebfb08537ef3b2c515d14c6640356e47fb90902110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0d29510cd0aed8daa82074bfa466b1db4be23ad3901c94e6a74e322e5491dea 0.600000000000 1483030 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": 1019149, "vin": [ { "gen": { "height": 1019139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0d29510cd0aed8daa82074bfa466b1db4be23ad3901c94e6a74e322e5491dea" } } ], "extra": [ 1, 202, 14, 122, 216, 21, 38, 186, 24, 55, 122, 210, 146, 232, 78, 191, 176, 133, 55, 239, 59, 44, 81, 93, 20, 198, 100, 3, 86, 228, 127, 185, 9, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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