Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53cd71f2ad146da7d78248384f05fb614c51b3ede8f69c84edf97947d5d4ba29

Tx prefix hash: 61cc9fe92013aff811ba9a2ecd017f229f92e900712ab3c827e978f3c2d4afc4
Tx public key: f10d14543623f522c61b37a23663ccf1dcb9ea908acd40a126e638ad64cc0670
Timestamp: 1709051618 Timestamp [UCT]: 2024-02-27 16:33:38 Age [y:d:h:m:s]: 01:092:11:36:10
Block: 966794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327152 RingCT/type: yes/0
Extra: 01f10d14543623f522c61b37a23663ccf1dcb9ea908acd40a126e638ad64cc067002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7df1e2bea0cdea5fcddbb2a9dc022e889710e76cad5327ceea4ede0f1811ffa 0.600000000000 1426565 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": 966804, "vin": [ { "gen": { "height": 966794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7df1e2bea0cdea5fcddbb2a9dc022e889710e76cad5327ceea4ede0f1811ffa" } } ], "extra": [ 1, 241, 13, 20, 84, 54, 35, 245, 34, 198, 27, 55, 162, 54, 99, 204, 241, 220, 185, 234, 144, 138, 205, 64, 161, 38, 230, 56, 173, 100, 204, 6, 112, 2, 17, 0, 0, 0, 5, 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