Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 692878fa1581e42d7134efe87336084ef8042a3746da25b10b4d72ad32a1440d

Tx prefix hash: a55b24d8c40159f83e4ae5fb5503dff94d02af0b9371b3eaa49f0925c65ea0b3
Tx public key: be8ccec0360bcdd8d76a77cc687a20cb36a3aba5c2716c12881eb8ab043c7d11
Timestamp: 1716313524 Timestamp [UCT]: 2024-05-21 17:45:24 Age [y:d:h:m:s]: 00:187:04:55:10
Block: 1026995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133997 RingCT/type: yes/0
Extra: 01be8ccec0360bcdd8d76a77cc687a20cb36a3aba5c2716c12881eb8ab043c7d1102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264a95ad8f01aba1d9455dbd5e3d0da896f06e24a4bdb86973c3673ccb75d802 0.600000000000 1494386 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": 1027005, "vin": [ { "gen": { "height": 1026995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264a95ad8f01aba1d9455dbd5e3d0da896f06e24a4bdb86973c3673ccb75d802" } } ], "extra": [ 1, 190, 140, 206, 192, 54, 11, 205, 216, 215, 106, 119, 204, 104, 122, 32, 203, 54, 163, 171, 165, 194, 113, 108, 18, 136, 30, 184, 171, 4, 60, 125, 17, 2, 17, 0, 0, 0, 2, 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