Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05fd1578ae0a4a5f79f6801b9b4a4c046245df8e97ba4853f6a29c1e7e9cc85

Tx prefix hash: a102228b65899ca7cafb777a65d417c03236caa371498c8ce970bd2b23d3b341
Tx public key: c0957152593826ce261ebba090d16d00754c049f54f5fb953fac684f86dd7766
Timestamp: 1712163697 Timestamp [UCT]: 2024-04-03 17:01:37 Age [y:d:h:m:s]: 00:342:22:46:06
Block: 992567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245224 RingCT/type: yes/0
Extra: 01c0957152593826ce261ebba090d16d00754c049f54f5fb953fac684f86dd776602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9fca0ea5ae1e012bb3528e81fcc9fe10d2ab2d62609e7640b27aa9dba227cb1 0.600000000000 1452921 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": 992577, "vin": [ { "gen": { "height": 992567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9fca0ea5ae1e012bb3528e81fcc9fe10d2ab2d62609e7640b27aa9dba227cb1" } } ], "extra": [ 1, 192, 149, 113, 82, 89, 56, 38, 206, 38, 30, 187, 160, 144, 209, 109, 0, 117, 76, 4, 159, 84, 245, 251, 149, 63, 172, 104, 79, 134, 221, 119, 102, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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