Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe8e7cf34f0b47acb3e71abe872ab8a6f6627491b42cebc87f9cc74e2cfa426b

Tx prefix hash: 64812936aa7e3662d3a165c2192221b07ea43f3d852e0c7a0521f7d10b0ac392
Tx public key: c9bbc1b5ae38d0575e5eff6702e249709957be303559c0f4df909add1ef47774
Timestamp: 1718282447 Timestamp [UCT]: 2024-06-13 12:40:47 Age [y:d:h:m:s]: 01:147:06:55:37
Block: 1043316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363825 RingCT/type: yes/0
Extra: 01c9bbc1b5ae38d0575e5eff6702e249709957be303559c0f4df909add1ef477740211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 141d9e3ab0ea983a7d9da09ebfdf42e71be67d65419b33bc8256be1370bfb158 0.600000000000 1512441 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": 1043326, "vin": [ { "gen": { "height": 1043316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "141d9e3ab0ea983a7d9da09ebfdf42e71be67d65419b33bc8256be1370bfb158" } } ], "extra": [ 1, 201, 187, 193, 181, 174, 56, 208, 87, 94, 94, 255, 103, 2, 226, 73, 112, 153, 87, 190, 48, 53, 89, 192, 244, 223, 144, 154, 221, 30, 244, 119, 116, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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