Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 323c0f5ed067a3fe224b6a119265d3f48985624b64684047d8d3715df69853b1

Tx prefix hash: 6893c831dc6bf2362558c8891c02e46c47331287ff7de71b9561dc0f679171ef
Tx public key: b2fd4483e5af189f0393ff40c77f3118ce1f157e283a88fb39ab615e8cede5be
Timestamp: 1659618182 Timestamp [UCT]: 2022-08-04 13:03:02 Age [y:d:h:m:s]: 02:157:02:42:49
Block: 558545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633719 RingCT/type: yes/0
Extra: 01b2fd4483e5af189f0393ff40c77f3118ce1f157e283a88fb39ab615e8cede5be02110000000265468698000000000000000000

1 output(s) for total of 8.655829071000 dcy

stealth address amount amount idx
00: 5c992095adcdcc83c5ea8b73d5e88c563e2d9efa136ad8164dcb8216ace33278 8.655829071000 990631 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": 558555, "vin": [ { "gen": { "height": 558545 } } ], "vout": [ { "amount": 8655829071, "target": { "key": "5c992095adcdcc83c5ea8b73d5e88c563e2d9efa136ad8164dcb8216ace33278" } } ], "extra": [ 1, 178, 253, 68, 131, 229, 175, 24, 159, 3, 147, 255, 64, 199, 127, 49, 24, 206, 31, 21, 126, 40, 58, 136, 251, 57, 171, 97, 94, 140, 237, 229, 190, 2, 17, 0, 0, 0, 2, 101, 70, 134, 152, 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