Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43db539fc6769ddb9c9d9f385dd7561bbd6b912aa357f04f6174992e8739f762

Tx prefix hash: b6cc677b750535a0df3b4ae836ca935dcd2467d803bda13c6c95ba071ebb7403
Tx public key: d95816634aa2abd2d8cf5901cd728a59e6c02067ee9b33bb21076ad6c6ff609a
Timestamp: 1720253495 Timestamp [UCT]: 2024-07-06 08:11:35 Age [y:d:h:m:s]: 00:108:21:22:52
Block: 1059651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77972 RingCT/type: yes/0
Extra: 01d95816634aa2abd2d8cf5901cd728a59e6c02067ee9b33bb21076ad6c6ff609a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85f78945a29ce5f5c374271867546dd6fa4c9e8c6b9bc136de8ec36cc5ee4b5e 0.600000000000 1530122 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": 1059661, "vin": [ { "gen": { "height": 1059651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85f78945a29ce5f5c374271867546dd6fa4c9e8c6b9bc136de8ec36cc5ee4b5e" } } ], "extra": [ 1, 217, 88, 22, 99, 74, 162, 171, 210, 216, 207, 89, 1, 205, 114, 138, 89, 230, 192, 32, 103, 238, 155, 51, 187, 33, 7, 106, 214, 198, 255, 96, 154, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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