Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4010216d5cfd7218bc16c7101a46b00371cf47c8b35f85a0d434c0f84a3fb8a4

Tx prefix hash: 824fe64dde681a5945c1c99d72adbd7784f5900932081b493a6925a06619ece9
Tx public key: a14f1ac2b582cf52ff6ccf4287b2496520c5d7a3ba5eb82b90e720a73336ac79
Timestamp: 1721107854 Timestamp [UCT]: 2024-07-16 05:30:54 Age [y:d:h:m:s]: 00:241:19:29:02
Block: 1066757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172742 RingCT/type: yes/0
Extra: 01a14f1ac2b582cf52ff6ccf4287b2496520c5d7a3ba5eb82b90e720a73336ac7902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4462d269a4af5a4931712ea48b0d7a27cdfbcd071b3a82d53a1086050b6d6272 0.600000000000 1537424 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": 1066767, "vin": [ { "gen": { "height": 1066757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4462d269a4af5a4931712ea48b0d7a27cdfbcd071b3a82d53a1086050b6d6272" } } ], "extra": [ 1, 161, 79, 26, 194, 181, 130, 207, 82, 255, 108, 207, 66, 135, 178, 73, 101, 32, 197, 215, 163, 186, 94, 184, 43, 144, 231, 32, 167, 51, 54, 172, 121, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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