Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecd03d25ddd138f1f3c6913b92b3199eacb4544cd75f86ea972366b7126b7846

Tx prefix hash: 3a15d285b5394d5f53aea7732bd84b29f8fe7eb43e735c1294ccceb671c1ee8e
Tx public key: cf48e882c308c1f5d64e0fdac01fe6b41eb1f37d3ac1a1410a7f27a31a740cf4
Timestamp: 1707835822 Timestamp [UCT]: 2024-02-13 14:50:22 Age [y:d:h:m:s]: 01:062:06:33:54
Block: 956703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305554 RingCT/type: yes/0
Extra: 01cf48e882c308c1f5d64e0fdac01fe6b41eb1f37d3ac1a1410a7f27a31a740cf40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2041dceeab6161f5c162fc7fbee72431a08ec57d09e9a0472d07cd425d99d33e 0.600000000000 1416013 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": 956713, "vin": [ { "gen": { "height": 956703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2041dceeab6161f5c162fc7fbee72431a08ec57d09e9a0472d07cd425d99d33e" } } ], "extra": [ 1, 207, 72, 232, 130, 195, 8, 193, 245, 214, 78, 15, 218, 192, 31, 230, 180, 30, 177, 243, 125, 58, 193, 161, 65, 10, 127, 39, 163, 26, 116, 12, 244, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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