Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c827b9143ba9058f250adcc3f46b2c3a7faddb288183c7aedb305bcafeb17b

Tx prefix hash: d54d7e2352159e54853b4bcceecf163b66d4b7b91b95ba71d0ff4d681556579f
Tx public key: 0f2dd5d1df851292f14fb65dd0c583797554a56fa39f2a488d59f039ca89dc75
Timestamp: 1732065417 Timestamp [UCT]: 2024-11-20 01:16:57 Age [y:d:h:m:s]: 00:116:01:45:34
Block: 1157493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82777 RingCT/type: yes/0
Extra: 010f2dd5d1df851292f14fb65dd0c583797554a56fa39f2a488d59f039ca89dc750211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcacebc339313662190e15b1ac2fdcbe234d3d32325bbcf60d857e78e2d9442b 0.600000000000 1643116 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": 1157503, "vin": [ { "gen": { "height": 1157493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcacebc339313662190e15b1ac2fdcbe234d3d32325bbcf60d857e78e2d9442b" } } ], "extra": [ 1, 15, 45, 213, 209, 223, 133, 18, 146, 241, 79, 182, 93, 208, 197, 131, 121, 117, 84, 165, 111, 163, 159, 42, 72, 141, 89, 240, 57, 202, 137, 220, 117, 2, 17, 0, 0, 0, 5, 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