Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca21dd0d9df720557297b0964fc49f4e70989ca01407027b65588856dc70b5eb

Tx prefix hash: 6261a38a9e543b5bb1b292abc051f1196ca60620aefba4eb511aa207c65dc6f4
Tx public key: 42f016de654f54e8710dc7a2cf6c2b2cb834237e7cb4f97be251d4161e34260f
Timestamp: 1707417394 Timestamp [UCT]: 2024-02-08 18:36:34 Age [y:d:h:m:s]: 01:035:06:08:53
Block: 953231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286255 RingCT/type: yes/0
Extra: 0142f016de654f54e8710dc7a2cf6c2b2cb834237e7cb4f97be251d4161e34260f02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d30784ced5e898f17840de5e1d967aaad5a87f252295695d0ea9be34671165ba 0.600000000000 1412417 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": 953241, "vin": [ { "gen": { "height": 953231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d30784ced5e898f17840de5e1d967aaad5a87f252295695d0ea9be34671165ba" } } ], "extra": [ 1, 66, 240, 22, 222, 101, 79, 84, 232, 113, 13, 199, 162, 207, 108, 43, 44, 184, 52, 35, 126, 124, 180, 249, 123, 226, 81, 212, 22, 30, 52, 38, 15, 2, 17, 0, 0, 0, 8, 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