Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0b6351a1e88b8da4ca891770f3a779343697610765344943388fa78655e02c

Tx prefix hash: dccb4bd4581bf6b2cc1d4dc43a835a3e5f1daa35e060e352bc40f82cf9204d5f
Tx public key: 182dbfd5e40abf0e83b55703a1d04be23badc477f6637018f2d4b2fc52a185a2
Timestamp: 1708458422 Timestamp [UCT]: 2024-02-20 19:47:02 Age [y:d:h:m:s]: 01:005:09:39:41
Block: 961873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264845 RingCT/type: yes/0
Extra: 01182dbfd5e40abf0e83b55703a1d04be23badc477f6637018f2d4b2fc52a185a202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35ee642ca5c70ddd9394691f3d60e48b73b41b42d86710f293f5a59fd5c6c9c 0.600000000000 1421486 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": 961883, "vin": [ { "gen": { "height": 961873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35ee642ca5c70ddd9394691f3d60e48b73b41b42d86710f293f5a59fd5c6c9c" } } ], "extra": [ 1, 24, 45, 191, 213, 228, 10, 191, 14, 131, 181, 87, 3, 161, 208, 75, 226, 59, 173, 196, 119, 246, 99, 112, 24, 242, 212, 178, 252, 82, 161, 133, 162, 2, 17, 0, 0, 0, 3, 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