Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1035c205c1a61997136901613887f280b83433d0c82c95e40a730e29e2957b88

Tx prefix hash: f5973ff94ec4ba1515f929980dc1d7c5dc55eff2d3f6beb7cd18e1bf762d4a08
Tx public key: a6ec0d4681c714b002b665325874b259d6fb932c5ad5fd8f794584d3dc8ca991
Timestamp: 1711326795 Timestamp [UCT]: 2024-03-25 00:33:15 Age [y:d:h:m:s]: 01:051:05:46:32
Block: 985670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297606 RingCT/type: yes/0
Extra: 01a6ec0d4681c714b002b665325874b259d6fb932c5ad5fd8f794584d3dc8ca99102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6a705f8c5760e2bf5b59ae8ccc4d8d4c23c173c89c9ee8b7d31e6a34114331f 0.600000000000 1445887 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": 985680, "vin": [ { "gen": { "height": 985670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a705f8c5760e2bf5b59ae8ccc4d8d4c23c173c89c9ee8b7d31e6a34114331f" } } ], "extra": [ 1, 166, 236, 13, 70, 129, 199, 20, 176, 2, 182, 101, 50, 88, 116, 178, 89, 214, 251, 147, 44, 90, 213, 253, 143, 121, 69, 132, 211, 220, 140, 169, 145, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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