Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95e385ada099f0e7d2151ef03f71e5d35c2483c08599a80d48260a6ec1e5845

Tx prefix hash: 4f5e08c13c2461915892d23b67629a17850298db8599c9b80f3558cee47b034f
Tx public key: 77637b32de71c1933330a16c9ecc6804bee6ca6d2c7bc3b52026ae7a1d7c7d25
Timestamp: 1734882994 Timestamp [UCT]: 2024-12-22 15:56:34 Age [y:d:h:m:s]: 00:177:08:43:59
Block: 1180856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126445 RingCT/type: yes/0
Extra: 0177637b32de71c1933330a16c9ecc6804bee6ca6d2c7bc3b52026ae7a1d7c7d250211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d764f5d21e5e5ae7febbab276526db1be82131ebf275ce777df6c47846323b7 0.600000000000 1667271 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": 1180866, "vin": [ { "gen": { "height": 1180856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d764f5d21e5e5ae7febbab276526db1be82131ebf275ce777df6c47846323b7" } } ], "extra": [ 1, 119, 99, 123, 50, 222, 113, 193, 147, 51, 48, 161, 108, 158, 204, 104, 4, 190, 230, 202, 109, 44, 123, 195, 181, 32, 38, 174, 122, 29, 124, 125, 37, 2, 17, 0, 0, 0, 4, 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