Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2cc59a3b6dd1cb649d6465de186e4e1ce8f619d0a65a8986f86e8f0bdba3c9f

Tx prefix hash: 85811644798b6e0783749b676f7e04967f13d30e863a521cf2fd939b9070e2a3
Tx public key: f90541768a2541e7e61be8708f7f03db1f58122a81d16930b554df60f524e730
Timestamp: 1709150394 Timestamp [UCT]: 2024-02-28 19:59:54 Age [y:d:h:m:s]: 01:282:03:09:15
Block: 967612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460403 RingCT/type: yes/0
Extra: 01f90541768a2541e7e61be8708f7f03db1f58122a81d16930b554df60f524e73002110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb19cbf467c68dcc54262c00fce0d580cb71d300b8b57542d76c129fa657e2e 0.600000000000 1427395 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": 967622, "vin": [ { "gen": { "height": 967612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb19cbf467c68dcc54262c00fce0d580cb71d300b8b57542d76c129fa657e2e" } } ], "extra": [ 1, 249, 5, 65, 118, 138, 37, 65, 231, 230, 27, 232, 112, 143, 127, 3, 219, 31, 88, 18, 42, 129, 209, 105, 48, 181, 84, 223, 96, 245, 36, 231, 48, 2, 17, 0, 0, 0, 10, 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