Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b025f77f3005f4315af761d9ceb428b178e43913fd7ad47676965b4f316703

Tx prefix hash: 5c3fa8970bf51cedb5c4896c852e6785c79b8071829855b47514a33f6e65d377
Tx public key: e93a418538f0c1f671a56d2508b2b52ed8e4546e9248593de09fa5847a58c5f1
Timestamp: 1722882389 Timestamp [UCT]: 2024-08-05 18:26:29 Age [y:d:h:m:s]: 00:079:02:06:19
Block: 1081454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56618 RingCT/type: yes/0
Extra: 01e93a418538f0c1f671a56d2508b2b52ed8e4546e9248593de09fa5847a58c5f102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f329e9d0a8c87e3268ca1f0177740721ab933be447f57503467d059185f8d21c 0.600000000000 1555205 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": 1081464, "vin": [ { "gen": { "height": 1081454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f329e9d0a8c87e3268ca1f0177740721ab933be447f57503467d059185f8d21c" } } ], "extra": [ 1, 233, 58, 65, 133, 56, 240, 193, 246, 113, 165, 109, 37, 8, 178, 181, 46, 216, 228, 84, 110, 146, 72, 89, 61, 224, 159, 165, 132, 122, 88, 197, 241, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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