Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a4b3636543af0d698d3083547607d0a279b57737b3ee493dccd5006717371b6

Tx prefix hash: 2e15aa56d4bb0f5269a7b212f8f43e3babac882454273f5ce675393f1474eaaa
Tx public key: 7c7e4777d0e3689fe2e5c49812dfe52e1bd534f4c1e78ecee95caa3de1f59cb7
Timestamp: 1609521195 Timestamp [UCT]: 2021-01-01 17:13:15 Age [y:d:h:m:s]: 04:077:00:50:02
Block: 173207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068939 RingCT/type: yes/0
Extra: 017c7e4777d0e3689fe2e5c49812dfe52e1bd534f4c1e78ecee95caa3de1f59cb702110000001edf1e48bb000000000000000000

1 output(s) for total of 163.722741828000 dcy

stealth address amount amount idx
00: 36b7adeb6baf1eaf0e5ffdacb94c0c0e5b1e6922d2351291f0a56b149effe0f8 163.722741828000 328404 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": 173217, "vin": [ { "gen": { "height": 173207 } } ], "vout": [ { "amount": 163722741828, "target": { "key": "36b7adeb6baf1eaf0e5ffdacb94c0c0e5b1e6922d2351291f0a56b149effe0f8" } } ], "extra": [ 1, 124, 126, 71, 119, 208, 227, 104, 159, 226, 229, 196, 152, 18, 223, 229, 46, 27, 213, 52, 244, 193, 231, 142, 206, 233, 92, 170, 61, 225, 245, 156, 183, 2, 17, 0, 0, 0, 30, 223, 30, 72, 187, 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