Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca7f7a35215120b16c34f86dc98fefdd7979cac68afb845b55f676e3b29b2e26

Tx prefix hash: f2225baac932f1e3b2fdb254dff8eea1c8f7ca70b3a33c1b3c9646c4e1851795
Tx public key: c0e19bfee0944480532d2b84bf1583cd7ef3f728b206d5376ffd77688831ed8b
Timestamp: 1734702277 Timestamp [UCT]: 2024-12-20 13:44:37 Age [y:d:h:m:s]: 00:094:19:52:02
Block: 1179356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67527 RingCT/type: yes/0
Extra: 01c0e19bfee0944480532d2b84bf1583cd7ef3f728b206d5376ffd77688831ed8b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50c7475049c62af7d83683d52131541655fbb2eac8b8ebe3b1631f7d3d23dce7 0.600000000000 1665751 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": 1179366, "vin": [ { "gen": { "height": 1179356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50c7475049c62af7d83683d52131541655fbb2eac8b8ebe3b1631f7d3d23dce7" } } ], "extra": [ 1, 192, 225, 155, 254, 224, 148, 68, 128, 83, 45, 43, 132, 191, 21, 131, 205, 126, 243, 247, 40, 178, 6, 213, 55, 111, 253, 119, 104, 136, 49, 237, 139, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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