Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4273298f29e93174eafa9ceac082eab9931973d3cda4307a0eb45722df05a09

Tx prefix hash: 344a568f38e963b3b8504535e005d7b9e6ce792a4dde5b346260f11a2764fce1
Tx public key: 5dfa93708977a0e057dc0463d6f27a0b4bb37fd05bf21f89e2e31c17ccf5cf2d
Timestamp: 1750281792 Timestamp [UCT]: 2025-06-18 21:23:12 Age [y:d:h:m:s]: 00:154:04:52:12
Block: 1307906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108031 RingCT/type: yes/0
Extra: 015dfa93708977a0e057dc0463d6f27a0b4bb37fd05bf21f89e2e31c17ccf5cf2d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a40907bd044178e0ddf72a698584f71f1930a20e9d6e513eaed5d2a4997a858f 0.600000000000 1795517 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": 1307916, "vin": [ { "gen": { "height": 1307906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a40907bd044178e0ddf72a698584f71f1930a20e9d6e513eaed5d2a4997a858f" } } ], "extra": [ 1, 93, 250, 147, 112, 137, 119, 160, 224, 87, 220, 4, 99, 214, 242, 122, 11, 75, 179, 127, 208, 91, 242, 31, 137, 226, 227, 28, 23, 204, 245, 207, 45, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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