Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29e93521799d777ca79170a2489083ae0a6f63c40daad5545071061d99a5a53

Tx prefix hash: 6abe2dfd6198d27ec8f7d34abaf6381e816abcc5a7a9c9f0f4cd894fb432016d
Tx public key: 6f14367d1e2b0d005934265b77c91816c3d83eef60deb38ad54b5dc49a929a67
Timestamp: 1762004061 Timestamp [UCT]: 2025-11-01 13:34:21 Age [y:d:h:m:s]: 00:013:10:31:21
Block: 1402694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9595 RingCT/type: yes/0
Extra: 016f14367d1e2b0d005934265b77c91816c3d83eef60deb38ad54b5dc49a929a670211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f370afd53675f6b1f2aa852ee075a68454274b20d963434dc97a5925f03d419d 0.600000000000 1891013 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": 1402704, "vin": [ { "gen": { "height": 1402694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f370afd53675f6b1f2aa852ee075a68454274b20d963434dc97a5925f03d419d" } } ], "extra": [ 1, 111, 20, 54, 125, 30, 43, 13, 0, 89, 52, 38, 91, 119, 201, 24, 22, 195, 216, 62, 239, 96, 222, 179, 138, 213, 75, 93, 196, 154, 146, 154, 103, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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