Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f73117b736ae628a85df5465a8b25ab208d5408e643739d1b679f23e6dd98a4

Tx prefix hash: c2c4fbcada03f4959b061f2104de792ab4bd7d97e81252cf9018e82fd1dfa7ce
Tx public key: 6961fc990608b426bc894a8f33aceec1613828e357b346ec2e1dcd6f6e8aab81
Timestamp: 1578859938 Timestamp [UCT]: 2020-01-12 20:12:18 Age [y:d:h:m:s]: 05:293:15:31:42
Block: 44177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357731 RingCT/type: yes/0
Extra: 016961fc990608b426bc894a8f33aceec1613828e357b346ec2e1dcd6f6e8aab81021100000013d81c26c0000000000000000000

1 output(s) for total of 438.151297156000 dcy

stealth address amount amount idx
00: e034a9af68ad654087951423af2a2e2a1eb8b08e9b511f674d95a043453b5991 438.151297156000 80309 of 0

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": 44187, "vin": [ { "gen": { "height": 44177 } } ], "vout": [ { "amount": 438151297156, "target": { "key": "e034a9af68ad654087951423af2a2e2a1eb8b08e9b511f674d95a043453b5991" } } ], "extra": [ 1, 105, 97, 252, 153, 6, 8, 180, 38, 188, 137, 74, 143, 51, 172, 238, 193, 97, 56, 40, 227, 87, 179, 70, 236, 46, 29, 205, 111, 110, 138, 171, 129, 2, 17, 0, 0, 0, 19, 216, 28, 38, 192, 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