Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d853e4164a728f9e8d630cfb8a36fffc5c9d3df9b620ef815bd537dadfd0b2a0

Tx prefix hash: 6690fe8e5249b2738897511fc30b7f0b1b7d67a95b76b640dfed6e080cf505b1
Tx public key: 8239280a94d52373f6511a185c467fb2ec964d1b738c912d579f3aa3562ac9f6
Timestamp: 1672610451 Timestamp [UCT]: 2023-01-01 22:00:51 Age [y:d:h:m:s]: 02:151:13:32:18
Block: 665538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 630058 RingCT/type: yes/0
Extra: 018239280a94d52373f6511a185c467fb2ec964d1b738c912d579f3aa3562ac9f602110000000152542ceb000000000000000000

1 output(s) for total of 3.826452194000 dcy

stealth address amount amount idx
00: 4b1b9a3dc0e9f0f646fdebaef3d3ce1e5941869adfd04e17bd7accc14833d83b 3.826452194000 1106587 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": 665548, "vin": [ { "gen": { "height": 665538 } } ], "vout": [ { "amount": 3826452194, "target": { "key": "4b1b9a3dc0e9f0f646fdebaef3d3ce1e5941869adfd04e17bd7accc14833d83b" } } ], "extra": [ 1, 130, 57, 40, 10, 148, 213, 35, 115, 246, 81, 26, 24, 92, 70, 127, 178, 236, 150, 77, 27, 115, 140, 145, 45, 87, 159, 58, 163, 86, 42, 201, 246, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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