Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e337d9a8789ded2abe8a433da7184a5ba5daa6ab482f7c9618cb24b7277394

Tx prefix hash: 285aaa8ac976aaca99cc2dceb75f9c435206c4af7d41a2e7b4271b85b2456c7f
Tx public key: 2f35792a46835f1a0e88214f8a7cce98333fe8e23d5fc0379e849e610d894509
Timestamp: 1696709255 Timestamp [UCT]: 2023-10-07 20:07:35 Age [y:d:h:m:s]: 02:042:21:22:42
Block: 864661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550300 RingCT/type: yes/0
Extra: 012f35792a46835f1a0e88214f8a7cce98333fe8e23d5fc0379e849e610d89450902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.837566318000 dcy

stealth address amount amount idx
00: 2c80bf6fc24fb355cef633c0ffe4576c1efe060729841167d6b3852e693a5303 0.837566318000 1319181 of 0

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": 864671, "vin": [ { "gen": { "height": 864661 } } ], "vout": [ { "amount": 837566318, "target": { "key": "2c80bf6fc24fb355cef633c0ffe4576c1efe060729841167d6b3852e693a5303" } } ], "extra": [ 1, 47, 53, 121, 42, 70, 131, 95, 26, 14, 136, 33, 79, 138, 124, 206, 152, 51, 63, 232, 226, 61, 95, 192, 55, 158, 132, 158, 97, 13, 137, 69, 9, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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