Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b537f7965982da9546e1fca5ac43457b881444100eadb51629cbcc129b0980

Tx prefix hash: f058d88f80b7cc80f68e979e93bd1f3a5f0eb2de04fdbefd88a776fad063e886
Tx public key: 89c0d62c221e5b74d5dfe92fcbbbc98a43c47d49b862f9c7c44c3a9213216171
Timestamp: 1722387225 Timestamp [UCT]: 2024-07-31 00:53:45 Age [y:d:h:m:s]: 00:310:07:11:20
Block: 1077349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221716 RingCT/type: yes/0
Extra: 0189c0d62c221e5b74d5dfe92fcbbbc98a43c47d49b862f9c7c44c3a921321617102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21ec860987e3c43e36e28764861fc2bf08933bd2d5cb337ee35bcba48a018571 0.600000000000 1549896 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": 1077359, "vin": [ { "gen": { "height": 1077349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21ec860987e3c43e36e28764861fc2bf08933bd2d5cb337ee35bcba48a018571" } } ], "extra": [ 1, 137, 192, 214, 44, 34, 30, 91, 116, 213, 223, 233, 47, 203, 187, 201, 138, 67, 196, 125, 73, 184, 98, 249, 199, 196, 76, 58, 146, 19, 33, 97, 113, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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