Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0483def0e9f5fb9751a408da715ecc2fef6e09df40d195dff0fea390dd13a0f

Tx prefix hash: 54b0898085781f2836d04523d4070ced6f4784bf591bf2c20d057190b4075ca1
Tx public key: 522b4deed933db8b30c93b434556e4d9ed1be536bc3d19fe1483c1b1061cc4d2
Timestamp: 1710338955 Timestamp [UCT]: 2024-03-13 14:09:15 Age [y:d:h:m:s]: 01:023:19:35:29
Block: 977479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277995 RingCT/type: yes/0
Extra: 01522b4deed933db8b30c93b434556e4d9ed1be536bc3d19fe1483c1b1061cc4d202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c62a1ba680fcdfaed4616be254c6b48245143181b9def2a3306dfdd9d7cb52 0.600000000000 1437482 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": 977489, "vin": [ { "gen": { "height": 977479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c62a1ba680fcdfaed4616be254c6b48245143181b9def2a3306dfdd9d7cb52" } } ], "extra": [ 1, 82, 43, 77, 238, 217, 51, 219, 139, 48, 201, 59, 67, 69, 86, 228, 217, 237, 27, 229, 54, 188, 61, 25, 254, 20, 131, 193, 177, 6, 28, 196, 210, 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