Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17137de169a83c51772dedcf3166c122803b263936e6fd12168d2c27521ccf3

Tx prefix hash: 34e614ab5ae4ea719d482c1f720da99fc428bf1e8fa675f08d046461d7857b61
Tx public key: a9dd6f2c0c3f2c21deaf6d251ba07912563a40138333846a978f284cc0489e85
Timestamp: 1709651437 Timestamp [UCT]: 2024-03-05 15:10:37 Age [y:d:h:m:s]: 01:028:17:54:28
Block: 971765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281536 RingCT/type: yes/0
Extra: 01a9dd6f2c0c3f2c21deaf6d251ba07912563a40138333846a978f284cc0489e850211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a5eac71a85467efb6f6cba3924ae21a389810ab933527cd154055e3d2620e9d 0.600000000000 1431666 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": 971775, "vin": [ { "gen": { "height": 971765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a5eac71a85467efb6f6cba3924ae21a389810ab933527cd154055e3d2620e9d" } } ], "extra": [ 1, 169, 221, 111, 44, 12, 63, 44, 33, 222, 175, 109, 37, 27, 160, 121, 18, 86, 58, 64, 19, 131, 51, 132, 106, 151, 143, 40, 76, 192, 72, 158, 133, 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