Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7462f9dd6b2278faafacc5fa53823af239d03a1503c4a3c0547c6cb6c19e8998

Tx prefix hash: 6eafe764e5223f6d2d2d7d77182cdc854767f89c010cb92c302f5f2801e3d003
Tx public key: e136d8a35b83b7b31105b8f9e357ddac4e4fd28fd814557ac9dd94989e3530de
Timestamp: 1733563241 Timestamp [UCT]: 2024-12-07 09:20:41 Age [y:d:h:m:s]: 00:124:16:35:41
Block: 1169897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88918 RingCT/type: yes/0
Extra: 01e136d8a35b83b7b31105b8f9e357ddac4e4fd28fd814557ac9dd94989e3530de02110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e8ce1a74c7657426d194a3fca1f8c32089697507a1813e2babcfba781541b08 0.600000000000 1655622 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": 1169907, "vin": [ { "gen": { "height": 1169897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e8ce1a74c7657426d194a3fca1f8c32089697507a1813e2babcfba781541b08" } } ], "extra": [ 1, 225, 54, 216, 163, 91, 131, 183, 179, 17, 5, 184, 249, 227, 87, 221, 172, 78, 79, 210, 143, 216, 20, 85, 122, 201, 221, 148, 152, 158, 53, 48, 222, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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