Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411c5082ce080d19d41aa0aa1e339642c8d28480eaf84050756cd5e1237b755d

Tx prefix hash: bf895ee2dd75e2db0cc3128699d24ed125d3c0eca0942e82be603d97e59f935d
Tx public key: faffeec7d6b4d18ffe0039e4c7cf37e831fef6f75c5c562ee004ccf3d3adfd9e
Timestamp: 1718467753 Timestamp [UCT]: 2024-06-15 16:09:13 Age [y:d:h:m:s]: 00:273:04:47:29
Block: 1044861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195229 RingCT/type: yes/0
Extra: 01faffeec7d6b4d18ffe0039e4c7cf37e831fef6f75c5c562ee004ccf3d3adfd9e021100000001b27e313d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e664bbd69bb7bae06c198a57b8c8f6154387157a573375232c0ad516125bd93b 0.600000000000 1514282 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": 1044871, "vin": [ { "gen": { "height": 1044861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e664bbd69bb7bae06c198a57b8c8f6154387157a573375232c0ad516125bd93b" } } ], "extra": [ 1, 250, 255, 238, 199, 214, 180, 209, 143, 254, 0, 57, 228, 199, 207, 55, 232, 49, 254, 246, 247, 92, 92, 86, 46, 224, 4, 204, 243, 211, 173, 253, 158, 2, 17, 0, 0, 0, 1, 178, 126, 49, 61, 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