Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c23b6beb4bfdbef6e76dba622b16eb19d8a66310a3c539d0250777b3524861

Tx prefix hash: 0ed495113aff2b2f161ac5e2ae701d25190f9424b7b5a1a7600a9732aaea7143
Tx public key: 23ff7a396c31e5c3e1d34040817e2499fb29d6dc5967b62a376a3f8ee86b9538
Timestamp: 1722671020 Timestamp [UCT]: 2024-08-03 07:43:40 Age [y:d:h:m:s]: 00:117:14:40:59
Block: 1079699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84139 RingCT/type: yes/0
Extra: 0123ff7a396c31e5c3e1d34040817e2499fb29d6dc5967b62a376a3f8ee86b953802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a228e9576fb5ef506b012ef1b139675bce28415d3feb80bba73d690d23dacd4 0.600000000000 1552770 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": 1079709, "vin": [ { "gen": { "height": 1079699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a228e9576fb5ef506b012ef1b139675bce28415d3feb80bba73d690d23dacd4" } } ], "extra": [ 1, 35, 255, 122, 57, 108, 49, 229, 195, 225, 211, 64, 64, 129, 126, 36, 153, 251, 41, 214, 220, 89, 103, 182, 42, 55, 106, 63, 142, 232, 107, 149, 56, 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