Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 080c84d5c1cd8b445a40c81ef5381af3d3e05a1a45e46b5fa1d9319e4d17149a

Tx prefix hash: b3c8ed87b34b399764b7e40dfa616d0a87729640ba55ce1e3f54b0f803a9235d
Tx public key: c6b131a031bc8fe21acb10864657c9369e45b3dd23e1b3060c2602692e67ad70
Timestamp: 1584528280 Timestamp [UCT]: 2020-03-18 10:44:40 Age [y:d:h:m:s]: 04:077:05:58:00
Block: 84937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950631 RingCT/type: yes/0
Extra: 01c6b131a031bc8fe21acb10864657c9369e45b3dd23e1b3060c2602692e67ad70021100000004c2c2f844000000000000000000

1 output(s) for total of 321.047463243000 dcy

stealth address amount amount idx
00: bddfa6f9c176602eed88897789b32cc025d866a1549674b52c49efd7888d4047 321.047463243000 153731 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": 84947, "vin": [ { "gen": { "height": 84937 } } ], "vout": [ { "amount": 321047463243, "target": { "key": "bddfa6f9c176602eed88897789b32cc025d866a1549674b52c49efd7888d4047" } } ], "extra": [ 1, 198, 177, 49, 160, 49, 188, 143, 226, 26, 203, 16, 134, 70, 87, 201, 54, 158, 69, 179, 221, 35, 225, 179, 6, 12, 38, 2, 105, 46, 103, 173, 112, 2, 17, 0, 0, 0, 4, 194, 194, 248, 68, 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