Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57feb406a3495c3c04b6a41a3bfe6ab8e4fa792de04d2c00aaca43bbb28f6938

Tx prefix hash: c9180ee14ac6f1d2e4a13caafb7b5333b1f2c3ae61c5ee824a210227826d5149
Tx public key: 48c1fa3450275905a0e665f1765933c9be4d5bac0347c02f9a6b231dfb136b88
Timestamp: 1723397606 Timestamp [UCT]: 2024-08-11 17:33:26 Age [y:d:h:m:s]: 01:089:08:18:21
Block: 1085728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322318 RingCT/type: yes/0
Extra: 0148c1fa3450275905a0e665f1765933c9be4d5bac0347c02f9a6b231dfb136b8802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c8e9a362e5d4d0b63751380b3ca1594b7c9d8dc5c3d7ee3185a3f5ebd585b67 0.600000000000 1560317 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": 1085738, "vin": [ { "gen": { "height": 1085728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c8e9a362e5d4d0b63751380b3ca1594b7c9d8dc5c3d7ee3185a3f5ebd585b67" } } ], "extra": [ 1, 72, 193, 250, 52, 80, 39, 89, 5, 160, 230, 101, 241, 118, 89, 51, 201, 190, 77, 91, 172, 3, 71, 192, 47, 154, 107, 35, 29, 251, 19, 107, 136, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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