Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b93c6d96345c982d1bddc864ff7527d5937d78c111c4669caa9e6597f4dc2b5b

Tx prefix hash: 4069a7be85d234e1fdfaedbcc8c428baa7c9e3ce04cedf6210b6298019c3aabc
Tx public key: 735799f339cc3e57d9398cde42d322e3b4161639c37a8196f65e34128d7de723
Timestamp: 1738292094 Timestamp [UCT]: 2025-01-31 02:54:54 Age [y:d:h:m:s]: 00:042:09:43:15
Block: 1208784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30348 RingCT/type: yes/0
Extra: 01735799f339cc3e57d9398cde42d322e3b4161639c37a8196f65e34128d7de723021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0161e1a409e333f3a08cf34099842d66d7dcf876411b98b1a26ea26b2df26d2 0.600000000000 1695519 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": 1208794, "vin": [ { "gen": { "height": 1208784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0161e1a409e333f3a08cf34099842d66d7dcf876411b98b1a26ea26b2df26d2" } } ], "extra": [ 1, 115, 87, 153, 243, 57, 204, 62, 87, 217, 57, 140, 222, 66, 211, 34, 227, 180, 22, 22, 57, 195, 122, 129, 150, 246, 94, 52, 18, 141, 125, 231, 35, 2, 17, 0, 0, 0, 1, 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