Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e58ca26fde04618dd71e042222ac8f79b8af91473b85c992293cd7465fc800

Tx prefix hash: 78c5fab0dbe97850e2c41b494d014fb307865f7d600c8a0e909101f31cc66e2b
Tx public key: ebd5d8515834dbc1b55eafe27f9dac34d17fdc76be9163aa3d1b85d9f40fdb64
Timestamp: 1737178846 Timestamp [UCT]: 2025-01-18 05:40:46 Age [y:d:h:m:s]: 00:058:06:46:31
Block: 1199833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41436 RingCT/type: yes/0
Extra: 01ebd5d8515834dbc1b55eafe27f9dac34d17fdc76be9163aa3d1b85d9f40fdb640211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4963ff122984a529df6bf26a6d0fcbc0544ec2576ffc1210a10e878ca14e609e 0.600000000000 1686466 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": 1199843, "vin": [ { "gen": { "height": 1199833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4963ff122984a529df6bf26a6d0fcbc0544ec2576ffc1210a10e878ca14e609e" } } ], "extra": [ 1, 235, 213, 216, 81, 88, 52, 219, 193, 181, 94, 175, 226, 127, 157, 172, 52, 209, 127, 220, 118, 190, 145, 99, 170, 61, 27, 133, 217, 244, 15, 219, 100, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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