Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c54df315a6e2bfdf720727ab51bf2de62846f634bc7c8babd24f5f343cb6ec

Tx prefix hash: 2f400999314ae1178b64f20c7ec3f379ae44f9f7e88d5701da4d91120231254d
Tx public key: bdc42ccd3c779617f5aea0fe9c40732cc9f5599548f41d1cf22458e5c8c11407
Timestamp: 1720648626 Timestamp [UCT]: 2024-07-10 21:57:06 Age [y:d:h:m:s]: 00:264:15:20:01
Block: 1062938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189052 RingCT/type: yes/0
Extra: 01bdc42ccd3c779617f5aea0fe9c40732cc9f5599548f41d1cf22458e5c8c11407021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea561f4933cb751bdd042a3d614cad506e935aa9c6bfa232543b927dec02d7c 0.600000000000 1533449 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": 1062948, "vin": [ { "gen": { "height": 1062938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea561f4933cb751bdd042a3d614cad506e935aa9c6bfa232543b927dec02d7c" } } ], "extra": [ 1, 189, 196, 44, 205, 60, 119, 150, 23, 245, 174, 160, 254, 156, 64, 115, 44, 201, 245, 89, 149, 72, 244, 29, 28, 242, 36, 88, 229, 200, 193, 20, 7, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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