Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b39f88c804b72256dc7c365dec3c3171faffea8f8ee55bd484b7f456e9e891

Tx prefix hash: a35ee5b098f338487841a806cf56d1ce215439340e7c586ae3a5ffc370053fcc
Tx public key: c52264adbb15ba476ad7a93522b02e7cd4e4f8a3baf993eb580a2db3db9a7fb0
Timestamp: 1746440961 Timestamp [UCT]: 2025-05-05 10:29:21 Age [y:d:h:m:s]: 00:156:17:07:55
Block: 1276233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109670 RingCT/type: yes/0
Extra: 01c52264adbb15ba476ad7a93522b02e7cd4e4f8a3baf993eb580a2db3db9a7fb00211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bfd36bc726f353610c207c4d8efe0f125932ed9986eac7179b3318d90a56a32 0.600000000000 1763558 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": 1276243, "vin": [ { "gen": { "height": 1276233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bfd36bc726f353610c207c4d8efe0f125932ed9986eac7179b3318d90a56a32" } } ], "extra": [ 1, 197, 34, 100, 173, 187, 21, 186, 71, 106, 215, 169, 53, 34, 176, 46, 124, 212, 228, 248, 163, 186, 249, 147, 235, 88, 10, 45, 179, 219, 154, 127, 176, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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