Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c4d33fad40ec061bb0864ad70f6bd5c122aa509a8de4ec2a40ad2f11443b9cc

Tx prefix hash: 2868c76e77916f0e94a23c73ebceeba2b85bbc268d78869faa097dc74982e315
Tx public key: e057f7bcbf5d1bf1452caa9ecdccc8cfa3a111e165a6b74c519743b56341d607
Timestamp: 1717554155 Timestamp [UCT]: 2024-06-05 02:22:35 Age [y:d:h:m:s]: 00:284:21:18:55
Block: 1037284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203601 RingCT/type: yes/0
Extra: 01e057f7bcbf5d1bf1452caa9ecdccc8cfa3a111e165a6b74c519743b56341d6070211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27acc728b515c7ca98a6e68b753ddeedde99db16b8c0ad0aeb31172113a43a3d 0.600000000000 1505815 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": 1037294, "vin": [ { "gen": { "height": 1037284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27acc728b515c7ca98a6e68b753ddeedde99db16b8c0ad0aeb31172113a43a3d" } } ], "extra": [ 1, 224, 87, 247, 188, 191, 93, 27, 241, 69, 44, 170, 158, 205, 204, 200, 207, 163, 161, 17, 225, 101, 166, 183, 76, 81, 151, 67, 181, 99, 65, 214, 7, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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