Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea385a94359caabfec4b2a78904fe9ff644fede139691a195c8b9da59d70e094

Tx prefix hash: 9e9ffbca6999ccd9c713d5245038d76f4d69d5dab4783a592c1a166f440149c9
Tx public key: fa8076a26ae60ec2eca10ee5141ee0cdae1f4d1d9f70e331bd67646ff599bf7f
Timestamp: 1733065175 Timestamp [UCT]: 2024-12-01 14:59:35 Age [y:d:h:m:s]: 00:356:02:49:46
Block: 1165774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252046 RingCT/type: yes/0
Extra: 01fa8076a26ae60ec2eca10ee5141ee0cdae1f4d1d9f70e331bd67646ff599bf7f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99d8e7aa9debf0b910d65d511ee0818b8507f432210ceed6a1e08809d06cb8ea 0.600000000000 1651449 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": 1165784, "vin": [ { "gen": { "height": 1165774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99d8e7aa9debf0b910d65d511ee0818b8507f432210ceed6a1e08809d06cb8ea" } } ], "extra": [ 1, 250, 128, 118, 162, 106, 230, 14, 194, 236, 161, 14, 229, 20, 30, 224, 205, 174, 31, 77, 29, 159, 112, 227, 49, 189, 103, 100, 111, 245, 153, 191, 127, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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