Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 385a63c5ec7af163b96daf726ae723b822003b501d867d0c154839bfedf5fda4

Tx prefix hash: b02ea0cdb33a7bd1142109d6b22a695f36ecbe1e71df44d5ae87b64618d03b5e
Tx public key: fb1f26bd67847dad65cf217708ee0f39d4eb1205d31f12eaaf3775f26c5f4cc8
Timestamp: 1718176340 Timestamp [UCT]: 2024-06-12 07:12:20 Age [y:d:h:m:s]: 00:337:14:30:40
Block: 1042446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241283 RingCT/type: yes/0
Extra: 01fb1f26bd67847dad65cf217708ee0f39d4eb1205d31f12eaaf3775f26c5f4cc80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a57ea3eb8a5e51a57986cc3450b37ceec9b86f7a20ffe64b03bd2e8ed1543f1 0.600000000000 1511367 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": 1042456, "vin": [ { "gen": { "height": 1042446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a57ea3eb8a5e51a57986cc3450b37ceec9b86f7a20ffe64b03bd2e8ed1543f1" } } ], "extra": [ 1, 251, 31, 38, 189, 103, 132, 125, 173, 101, 207, 33, 119, 8, 238, 15, 57, 212, 235, 18, 5, 211, 31, 18, 234, 175, 55, 117, 242, 108, 95, 76, 200, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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