Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4147251ada9bdb3d97d35313c5322bdfb3343c143bb81f3dcaeff3c9645a485f

Tx prefix hash: ab76d89ea68bf2e4f76a4d3d405636b250692cdfe258b32dbaeb2b7dcdcbac05
Tx public key: 5ae1a2bd5f16e90ded37d0d851472cedb9abb4b8c1406f0eb1735e9adc0e6527
Timestamp: 1762073770 Timestamp [UCT]: 2025-11-02 08:56:10 Age [y:d:h:m:s]: 00:062:01:49:06
Block: 1403247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44455 RingCT/type: yes/0
Extra: 015ae1a2bd5f16e90ded37d0d851472cedb9abb4b8c1406f0eb1735e9adc0e65270211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c161407c5809715cbd19fec1f6517a81e7387c07ce0fe842079ea7e88a8e27c9 0.600000000000 1891576 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": 1403257, "vin": [ { "gen": { "height": 1403247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c161407c5809715cbd19fec1f6517a81e7387c07ce0fe842079ea7e88a8e27c9" } } ], "extra": [ 1, 90, 225, 162, 189, 95, 22, 233, 13, 237, 55, 208, 216, 81, 71, 44, 237, 185, 171, 180, 184, 193, 64, 111, 14, 177, 115, 94, 154, 220, 14, 101, 39, 2, 17, 0, 0, 0, 2, 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