Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec76eb6d77ad2a9475a16e6d95855d16fa3eb267c802e27086b3301ec90ad1e

Tx prefix hash: ebfe53b8cf9f2d4a71381a4870aa39f17d77fbe2eb0c7a39ce8abd36c8b35f8c
Tx public key: 69400e9c22ae8a2c11e1629481c5a0056d37d3574115f5838929e8de298385a3
Timestamp: 1713687486 Timestamp [UCT]: 2024-04-21 08:18:06 Age [y:d:h:m:s]: 00:224:02:29:35
Block: 1005216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160440 RingCT/type: yes/0
Extra: 0169400e9c22ae8a2c11e1629481c5a0056d37d3574115f5838929e8de298385a30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69278c5c840b0890315570fd497484b203b2d4ddf2266a88c4d43d7973e5c558 0.600000000000 1465800 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": 1005226, "vin": [ { "gen": { "height": 1005216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69278c5c840b0890315570fd497484b203b2d4ddf2266a88c4d43d7973e5c558" } } ], "extra": [ 1, 105, 64, 14, 156, 34, 174, 138, 44, 17, 225, 98, 148, 129, 197, 160, 5, 109, 55, 211, 87, 65, 21, 245, 131, 137, 41, 232, 222, 41, 131, 133, 163, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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