Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43d9c80cd57e84668fce42a12f4a26711fe4af1028a6d628dc1de12cda585ac1

Tx prefix hash: 56bd36ff4145671d0fc632bbad2e58f49e3eb8acd6392e83ed0cd86976994417
Tx public key: df514aa8dc3ce5c4a3b22efcd82632cbd2806d2b3226cef7013b9ab27ac44edd
Timestamp: 1709496140 Timestamp [UCT]: 2024-03-03 20:02:20 Age [y:d:h:m:s]: 00:327:08:22:59
Block: 970479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234277 RingCT/type: yes/0
Extra: 01df514aa8dc3ce5c4a3b22efcd82632cbd2806d2b3226cef7013b9ab27ac44edd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71874aacc05b6e3916d39745e9d233f439c4d00d0acc57d1d7c3ee0771151629 0.600000000000 1430334 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": 970489, "vin": [ { "gen": { "height": 970479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71874aacc05b6e3916d39745e9d233f439c4d00d0acc57d1d7c3ee0771151629" } } ], "extra": [ 1, 223, 81, 74, 168, 220, 60, 229, 196, 163, 178, 46, 252, 216, 38, 50, 203, 210, 128, 109, 43, 50, 38, 206, 247, 1, 59, 154, 178, 122, 196, 78, 221, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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