Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb369ab13b55c24885664c2082cd11df02525049c6447fbe546c9833b3f0e63a

Tx prefix hash: 56a538aad093de2881b9a6ce7ad43566c1ea28642b15622a1e196f19781e3423
Tx public key: 7eacb40dd517e9f0bbf166b5534a7ba95d2b08d106d8c399ba2a4dc1d35e9dd2
Timestamp: 1719369929 Timestamp [UCT]: 2024-06-26 02:45:29 Age [y:d:h:m:s]: 01:160:04:53:03
Block: 1052315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373093 RingCT/type: yes/0
Extra: 017eacb40dd517e9f0bbf166b5534a7ba95d2b08d106d8c399ba2a4dc1d35e9dd20211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f500ed7830bdb9cd17ce115a0c706755fe3c8be75ba43e89422da3da185084aa 0.600000000000 1522638 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": 1052325, "vin": [ { "gen": { "height": 1052315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f500ed7830bdb9cd17ce115a0c706755fe3c8be75ba43e89422da3da185084aa" } } ], "extra": [ 1, 126, 172, 180, 13, 213, 23, 233, 240, 187, 241, 102, 181, 83, 74, 123, 169, 93, 43, 8, 209, 6, 216, 195, 153, 186, 42, 77, 193, 211, 94, 157, 210, 2, 17, 0, 0, 0, 2, 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