Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5387bb816061f81666cfcdf5608fe71e8e615f8d233e9024f50f87ffe408da0b

Tx prefix hash: bed6913740df845cd6fbea055bd283aa8f7e711cde63e408a7137c10b59a16d6
Tx public key: 2eded9003a57b02f1335057f28e4ed6e907022f9c8d1a1e30714b44a9cfae2a7
Timestamp: 1731060317 Timestamp [UCT]: 2024-11-08 10:05:17 Age [y:d:h:m:s]: 00:202:17:40:39
Block: 1149171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144760 RingCT/type: yes/0
Extra: 012eded9003a57b02f1335057f28e4ed6e907022f9c8d1a1e30714b44a9cfae2a70211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8542081101038047b132cd2194b4976b1784eee0f580037107be2a5ce6b186bb 0.600000000000 1634190 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": 1149181, "vin": [ { "gen": { "height": 1149171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8542081101038047b132cd2194b4976b1784eee0f580037107be2a5ce6b186bb" } } ], "extra": [ 1, 46, 222, 217, 0, 58, 87, 176, 47, 19, 53, 5, 127, 40, 228, 237, 110, 144, 112, 34, 249, 200, 209, 161, 227, 7, 20, 180, 74, 156, 250, 226, 167, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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