Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d4522e747cdac7599aaf118907fa89bb32b1e4827e446e3521c0dc67478d34

Tx prefix hash: ebe51f5e6173048acce16a3893d80b88eea1c2fadc1bb729354ada747cf6aa94
Tx public key: a5371f27e9d29c28b8c4f926af505368578c9216e9a731e79166186e352ab058
Timestamp: 1639127566 Timestamp [UCT]: 2021-12-10 09:12:46 Age [y:d:h:m:s]: 02:344:00:28:16
Block: 392388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 763919 RingCT/type: yes/0
Extra: 01a5371f27e9d29c28b8c4f926af505368578c9216e9a731e79166186e352ab0580211000000141cab2639000000000000000000

1 output(s) for total of 30.750772519000 dcy

stealth address amount amount idx
00: 211af6ab203fb7020c0f9b0000c1f1f0e35d0bb01f965cbd5a5c4949148e1c45 30.750772519000 789237 of 0

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": 392398, "vin": [ { "gen": { "height": 392388 } } ], "vout": [ { "amount": 30750772519, "target": { "key": "211af6ab203fb7020c0f9b0000c1f1f0e35d0bb01f965cbd5a5c4949148e1c45" } } ], "extra": [ 1, 165, 55, 31, 39, 233, 210, 156, 40, 184, 196, 249, 38, 175, 80, 83, 104, 87, 140, 146, 22, 233, 167, 49, 231, 145, 102, 24, 110, 53, 42, 176, 88, 2, 17, 0, 0, 0, 20, 28, 171, 38, 57, 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