Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fb646158a185f18eac601eaca46035a8a57fde993b4011b093823f8921476f9

Tx prefix hash: 690cd7d86006cadbb01d8c2ccf6f36ab506fe8d4e73b3178cf598d22d9c38cf0
Tx public key: 0a8a3f58708526d2aa36efc42f8017d59b210a87c99c22c64434de8a31bb1e96
Timestamp: 1732024724 Timestamp [UCT]: 2024-11-19 13:58:44 Age [y:d:h:m:s]: 00:353:15:18:09
Block: 1157152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250286 RingCT/type: yes/0
Extra: 010a8a3f58708526d2aa36efc42f8017d59b210a87c99c22c64434de8a31bb1e96021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ff6e23d3f8393e8732c647732bae4a4ff7f65f16519cbf56d53d3591ea6604 0.600000000000 1642775 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": 1157162, "vin": [ { "gen": { "height": 1157152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ff6e23d3f8393e8732c647732bae4a4ff7f65f16519cbf56d53d3591ea6604" } } ], "extra": [ 1, 10, 138, 63, 88, 112, 133, 38, 210, 170, 54, 239, 196, 47, 128, 23, 213, 155, 33, 10, 135, 201, 156, 34, 198, 68, 52, 222, 138, 49, 187, 30, 150, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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