Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe818fb96560b8708a124fdd66bb5ac3cfb2ae6af14c573ff4f500764073d33

Tx prefix hash: d4ee68c0097775f9cb6f005d0a93648c00513c60e627bbbfe37b373833635b55
Tx public key: ac98c0ab3a3235e9435fef2ac8fadee80784ae63f4e3605536f1ea7898d93132
Timestamp: 1711201279 Timestamp [UCT]: 2024-03-23 13:41:19 Age [y:d:h:m:s]: 01:020:03:14:42
Block: 984637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275341 RingCT/type: yes/0
Extra: 01ac98c0ab3a3235e9435fef2ac8fadee80784ae63f4e3605536f1ea7898d9313202110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e74c52599c0a3d662c091a3436b851acb6a73d1fdea530f9cbfd215d9d46ab20 0.600000000000 1444808 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": 984647, "vin": [ { "gen": { "height": 984637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e74c52599c0a3d662c091a3436b851acb6a73d1fdea530f9cbfd215d9d46ab20" } } ], "extra": [ 1, 172, 152, 192, 171, 58, 50, 53, 233, 67, 95, 239, 42, 200, 250, 222, 232, 7, 132, 174, 99, 244, 227, 96, 85, 54, 241, 234, 120, 152, 217, 49, 50, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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