Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d49d02361a3fea1a75154d7036d712698fc1ac5340c916049cc6cf45198c1b

Tx prefix hash: 5f64534d25442bca1f45c8498809d6a427e5e81d8e5949e3cd0e3420b169f759
Tx public key: feaa8b5f8dc271f9bd89d9aa61486e34b69aed7599d23ca3ca6344aae3188ec1
Timestamp: 1708252071 Timestamp [UCT]: 2024-02-18 10:27:51 Age [y:d:h:m:s]: 01:052:12:22:02
Block: 960159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298560 RingCT/type: yes/0
Extra: 01feaa8b5f8dc271f9bd89d9aa61486e34b69aed7599d23ca3ca6344aae3188ec10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86f81d335e116a91c90418407dbc0d7122dcaee45c2eb46834794b6ef130d906 0.600000000000 1419720 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": 960169, "vin": [ { "gen": { "height": 960159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86f81d335e116a91c90418407dbc0d7122dcaee45c2eb46834794b6ef130d906" } } ], "extra": [ 1, 254, 170, 139, 95, 141, 194, 113, 249, 189, 137, 217, 170, 97, 72, 110, 52, 182, 154, 237, 117, 153, 210, 60, 163, 202, 99, 68, 170, 227, 24, 142, 193, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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