Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765d9ddaa57de61642b35f464be39f39a87a4f8cf42f5b3dd4cfc68b660c1e5f

Tx prefix hash: 7736e83220d42bca52ece43243ea7b363f2a8d21f73c21c9695314fd1c29d78e
Tx public key: 462aa0c3ef8d1cdd4e2daf9ffc2b28a497c069d0771c227e1cea4a21d3c40e24
Timestamp: 1736846071 Timestamp [UCT]: 2025-01-14 09:14:31 Age [y:d:h:m:s]: 00:310:18:48:22
Block: 1197075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219616 RingCT/type: yes/0
Extra: 01462aa0c3ef8d1cdd4e2daf9ffc2b28a497c069d0771c227e1cea4a21d3c40e24021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c1cce968fbecb367bcf782520a2d4a71cbf840a05b85f06fbc63ff7a373cd95 0.600000000000 1683680 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": 1197085, "vin": [ { "gen": { "height": 1197075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c1cce968fbecb367bcf782520a2d4a71cbf840a05b85f06fbc63ff7a373cd95" } } ], "extra": [ 1, 70, 42, 160, 195, 239, 141, 28, 221, 78, 45, 175, 159, 252, 43, 40, 164, 151, 192, 105, 208, 119, 28, 34, 126, 28, 234, 74, 33, 211, 196, 14, 36, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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