Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd9d58462adbe2c11147db9cc0df209e4bbe1cd393a7e910aaa0346e087c6ca

Tx prefix hash: 13f81fd4f4b140ea6866d8d5021c7380a2863597d2baf07289e32246863b7221
Tx public key: a3d0e1a9225e0fd0a45cb1b4fa15084486c66fd31c8a459fbe68265386659e28
Timestamp: 1729112332 Timestamp [UCT]: 2024-10-16 20:58:52 Age [y:d:h:m:s]: 00:149:01:04:51
Block: 1133104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106301 RingCT/type: yes/0
Extra: 01a3d0e1a9225e0fd0a45cb1b4fa15084486c66fd31c8a459fbe68265386659e2802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 722f064c9119c60a3fb5c1fd15cd411d7792326da248dae95600e94dc97eff0c 0.600000000000 1616173 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": 1133114, "vin": [ { "gen": { "height": 1133104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722f064c9119c60a3fb5c1fd15cd411d7792326da248dae95600e94dc97eff0c" } } ], "extra": [ 1, 163, 208, 225, 169, 34, 94, 15, 208, 164, 92, 177, 180, 250, 21, 8, 68, 134, 198, 111, 211, 28, 138, 69, 159, 190, 104, 38, 83, 134, 101, 158, 40, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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