Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1318c5232cf3d48c9069d9dce4db71bc741934cf80e66a03b716239a9577ed7f

Tx prefix hash: 9766f9de8a5403fe63c68b46770cb4a6bd4af0362a27a9a617a1103279ac18c5
Tx public key: 7eac9fae2b806d5e57eb0321ad47974f0f6b92a6ecdc8b08754ca6e54e0ea2e0
Timestamp: 1678808071 Timestamp [UCT]: 2023-03-14 15:34:31 Age [y:d:h:m:s]: 02:022:10:22:03
Block: 716952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537567 RingCT/type: yes/0
Extra: 017eac9fae2b806d5e57eb0321ad47974f0f6b92a6ecdc8b08754ca6e54e0ea2e002110000000375e3f0e9000000000000000000

1 output(s) for total of 2.584879436000 dcy

stealth address amount amount idx
00: 55118ee30a9a4361e533a2e4d7f0a0daa68f80d5c80e4476fab3686147e09d28 2.584879436000 1161441 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": 716962, "vin": [ { "gen": { "height": 716952 } } ], "vout": [ { "amount": 2584879436, "target": { "key": "55118ee30a9a4361e533a2e4d7f0a0daa68f80d5c80e4476fab3686147e09d28" } } ], "extra": [ 1, 126, 172, 159, 174, 43, 128, 109, 94, 87, 235, 3, 33, 173, 71, 151, 79, 15, 107, 146, 166, 236, 220, 139, 8, 117, 76, 166, 229, 78, 14, 162, 224, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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