Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46d15de854d100f3ff0c362ec152438a150be652ff645151c75aa409707990f

Tx prefix hash: c70ce99792d4f2f06008f8946c8eff2ec92130de3e24c435319658b7534c09cf
Tx public key: 7c260eefa1845e1db2dafcf45ee7a6ab0c42b4aa943f44964a7e7e5991d824f1
Timestamp: 1721309756 Timestamp [UCT]: 2024-07-18 13:35:56 Age [y:d:h:m:s]: 00:251:00:16:51
Block: 1068436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179288 RingCT/type: yes/0
Extra: 017c260eefa1845e1db2dafcf45ee7a6ab0c42b4aa943f44964a7e7e5991d824f1021100000001c4a71b29000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75ccbae83d7d6c5a3e1e9f80629e6bdda82e0a6b8f9005160b39683ec7166c8e 0.600000000000 1539513 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": 1068446, "vin": [ { "gen": { "height": 1068436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75ccbae83d7d6c5a3e1e9f80629e6bdda82e0a6b8f9005160b39683ec7166c8e" } } ], "extra": [ 1, 124, 38, 14, 239, 161, 132, 94, 29, 178, 218, 252, 244, 94, 231, 166, 171, 12, 66, 180, 170, 148, 63, 68, 150, 74, 126, 126, 89, 145, 216, 36, 241, 2, 17, 0, 0, 0, 1, 196, 167, 27, 41, 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