Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc6578592b726e01754c47233c4056374015a28a4b816092b5c734973e3fc9da

Tx prefix hash: 2cf5eecb1739dba02c52fde8078d874ddfdd32e24ae237f030eaaffe515c964f
Tx public key: a28daaa1a385ceed94db13545c4bb44a95744befcc7b0353c348647c3e90c4c1
Timestamp: 1582273360 Timestamp [UCT]: 2020-02-21 08:22:40 Age [y:d:h:m:s]: 04:322:19:44:37
Block: 69358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123274 RingCT/type: yes/0
Extra: 01a28daaa1a385ceed94db13545c4bb44a95744befcc7b0353c348647c3e90c4c102110000001f8a2ee0d9000000000000000000

1 output(s) for total of 361.567143967000 dcy

stealth address amount amount idx
00: 84157437bbc202d6dc50d5d68b2d583d433abc6cb9ce6fa03dd12338e6baec1a 361.567143967000 127924 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": 69368, "vin": [ { "gen": { "height": 69358 } } ], "vout": [ { "amount": 361567143967, "target": { "key": "84157437bbc202d6dc50d5d68b2d583d433abc6cb9ce6fa03dd12338e6baec1a" } } ], "extra": [ 1, 162, 141, 170, 161, 163, 133, 206, 237, 148, 219, 19, 84, 92, 75, 180, 74, 149, 116, 75, 239, 204, 123, 3, 83, 195, 72, 100, 124, 62, 144, 196, 193, 2, 17, 0, 0, 0, 31, 138, 46, 224, 217, 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