Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 194f4597bd76a8c714115bb574097683b04a9ba5906299c4717f5ebadac3d11a

Tx prefix hash: 023722e4eed1a100cce706b1ac94363153eab9f114c61d282f8f0e11093bcf27
Tx public key: e5f7b4d19683638e7295c14032b89b92328280f9c6ae3eaf8b1767f6b444719d
Timestamp: 1701448816 Timestamp [UCT]: 2023-12-01 16:40:16 Age [y:d:h:m:s]: 01:084:16:52:51
Block: 903747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321660 RingCT/type: yes/0
Extra: 01e5f7b4d19683638e7295c14032b89b92328280f9c6ae3eaf8b1767f6b444719d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.621599997000 dcy

stealth address amount amount idx
00: a4ea383e9f87fe5cc2817080622b905646ccb63824143b960b874d15e54da4aa 0.621599997000 1360438 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": 903757, "vin": [ { "gen": { "height": 903747 } } ], "vout": [ { "amount": 621599997, "target": { "key": "a4ea383e9f87fe5cc2817080622b905646ccb63824143b960b874d15e54da4aa" } } ], "extra": [ 1, 229, 247, 180, 209, 150, 131, 99, 142, 114, 149, 193, 64, 50, 184, 155, 146, 50, 130, 128, 249, 198, 174, 62, 175, 139, 23, 103, 246, 180, 68, 113, 157, 2, 17, 0, 0, 0, 6, 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