Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ca468fc3eb4e0d5389bcaf6dbe42c836fb3494123c24766345aea0f1a79cf7

Tx prefix hash: 84822c787865b09b117d48abc423a30c1a76a53825f4da5d4bdd3f24e4547281
Tx public key: 23569ba5ce5ee85f630f5c079e7f0db92b977b9a902982850f49bd1f95039ce6
Timestamp: 1707455573 Timestamp [UCT]: 2024-02-09 05:12:53 Age [y:d:h:m:s]: 01:018:13:48:07
Block: 953550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274294 RingCT/type: yes/0
Extra: 0123569ba5ce5ee85f630f5c079e7f0db92b977b9a902982850f49bd1f95039ce602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3295cd5d0961d2add8ff55c5a13ed2222c277d6a5ef8b5a621f14f62a29564 0.600000000000 1412776 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": 953560, "vin": [ { "gen": { "height": 953550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3295cd5d0961d2add8ff55c5a13ed2222c277d6a5ef8b5a621f14f62a29564" } } ], "extra": [ 1, 35, 86, 155, 165, 206, 94, 232, 95, 99, 15, 92, 7, 158, 127, 13, 185, 43, 151, 123, 154, 144, 41, 130, 133, 15, 73, 189, 31, 149, 3, 156, 230, 2, 17, 0, 0, 0, 4, 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