Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56539c6dd4fbe832721b4c332f8e1b0291a8ffd6ce149cb2967771d1d6cdf569

Tx prefix hash: d69e1ca0ec98abdcc5f5c9a069c5ac810072871be1ac61ff60012f81c68c1f1b
Tx public key: a3aa5d376aff360a3f16f64a8ad894b7ae4333a24b9c87b2332b243676765254
Timestamp: 1750710092 Timestamp [UCT]: 2025-06-23 20:21:32 Age [y:d:h:m:s]: 00:147:12:57:32
Block: 1311339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103375 RingCT/type: yes/0
Extra: 01a3aa5d376aff360a3f16f64a8ad894b7ae4333a24b9c87b2332b24367676525402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f1871bd6422f6d98ea4705ef4e05e2008c13304a41abfe82eb940c2a1f0b189 0.600000000000 1798966 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": 1311349, "vin": [ { "gen": { "height": 1311339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f1871bd6422f6d98ea4705ef4e05e2008c13304a41abfe82eb940c2a1f0b189" } } ], "extra": [ 1, 163, 170, 93, 55, 106, 255, 54, 10, 63, 22, 246, 74, 138, 216, 148, 183, 174, 67, 51, 162, 75, 156, 135, 178, 51, 43, 36, 54, 118, 118, 82, 84, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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