Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88fc10e24b201b7b859b0bf3d7c7f153627bf53bd6d6767669662cb4f82b2869

Tx prefix hash: 473654c2bbd5e9f073fc85f6f32c3efa769691fe4f9b84108519e4f534ab1f5f
Tx public key: 4161a09311cf199e4574488536f0b7fdb7cc6fc0f8d4e81dc8f0af9c8a73b833
Timestamp: 1721101716 Timestamp [UCT]: 2024-07-16 03:48:36 Age [y:d:h:m:s]: 00:259:10:28:32
Block: 1066706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185318 RingCT/type: yes/0
Extra: 014161a09311cf199e4574488536f0b7fdb7cc6fc0f8d4e81dc8f0af9c8a73b83302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 210f5c8d8ae589471c19ac20519f3aa047a091baa2e97195ea7fd2584b2edc87 0.600000000000 1537373 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": 1066716, "vin": [ { "gen": { "height": 1066706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "210f5c8d8ae589471c19ac20519f3aa047a091baa2e97195ea7fd2584b2edc87" } } ], "extra": [ 1, 65, 97, 160, 147, 17, 207, 25, 158, 69, 116, 72, 133, 54, 240, 183, 253, 183, 204, 111, 192, 248, 212, 232, 29, 200, 240, 175, 156, 138, 115, 184, 51, 2, 17, 0, 0, 0, 7, 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