Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd13121c61cb7d49e26bf319878a7c546bd3231ec970a29c88446e8b563f0320

Tx prefix hash: 0de50a1be5f3df60904bc3636c8731638804c3f81f81377a276e51a4ad36fdef
Tx public key: 7dda6fb6793a54a6f5154681ba28726739d08aeeb4e08315dd515b9d8b7f23d7
Timestamp: 1757527172 Timestamp [UCT]: 2025-09-10 17:59:32 Age [y:d:h:m:s]: 00:076:20:27:19
Block: 1365572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55020 RingCT/type: yes/0
Extra: 017dda6fb6793a54a6f5154681ba28726739d08aeeb4e08315dd515b9d8b7f23d7021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ca8c586ccb1a13be534e80719172982c055ca423e2681fc6e90d98edb84a746 0.600000000000 1853611 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": 1365582, "vin": [ { "gen": { "height": 1365572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ca8c586ccb1a13be534e80719172982c055ca423e2681fc6e90d98edb84a746" } } ], "extra": [ 1, 125, 218, 111, 182, 121, 58, 84, 166, 245, 21, 70, 129, 186, 40, 114, 103, 57, 208, 138, 238, 180, 224, 131, 21, 221, 81, 91, 157, 139, 127, 35, 215, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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