Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ff0c10636c38022edaab879462ac4b58da0860a23311c4d7a1db8109c0da23

Tx prefix hash: f72f1b551cbcb14ce69e24bcbc6d2cf822a6e965aea2692d66dd719dbcaa982a
Tx public key: 7b1fba3a9917f8afe18f841dc6101284c5cfc667918015d8e8017d3da27a12e3
Timestamp: 1707089665 Timestamp [UCT]: 2024-02-04 23:34:25 Age [y:d:h:m:s]: 01:062:11:38:18
Block: 950508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305719 RingCT/type: yes/0
Extra: 017b1fba3a9917f8afe18f841dc6101284c5cfc667918015d8e8017d3da27a12e30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 405d016741657c8105cc8c76fa43d2575286cc9beda062d82dc7c41431aeb8bb 0.600000000000 1409140 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": 950518, "vin": [ { "gen": { "height": 950508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "405d016741657c8105cc8c76fa43d2575286cc9beda062d82dc7c41431aeb8bb" } } ], "extra": [ 1, 123, 31, 186, 58, 153, 23, 248, 175, 225, 143, 132, 29, 198, 16, 18, 132, 197, 207, 198, 103, 145, 128, 21, 216, 232, 1, 125, 61, 162, 122, 18, 227, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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