Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c2579d5c4e710eaeb328f872269f1c833b7dad366fe4cc8221de24eae338cc5

Tx prefix hash: 0237e028a49900f20a1b876df615bbf19cdd1e0e5be17371c9b409d0a6ab4444
Tx public key: 02d4a6d9ccf5ee0bdba8adf87896278f5e0c25e1cb483818cf0eecd2669508d7
Timestamp: 1583748211 Timestamp [UCT]: 2020-03-09 10:03:31 Age [y:d:h:m:s]: 04:251:17:29:10
Block: 78942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075033 RingCT/type: yes/0
Extra: 0102d4a6d9ccf5ee0bdba8adf87896278f5e0c25e1cb483818cf0eecd2669508d7021100000001640ff48f000000000000000000

1 output(s) for total of 336.072653574000 dcy

stealth address amount amount idx
00: 2a3eaec40e8cd75d2f48741edd49329ed8941cd2b8bca8df4f8ab80f64098efa 336.072653574000 144636 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": 78952, "vin": [ { "gen": { "height": 78942 } } ], "vout": [ { "amount": 336072653574, "target": { "key": "2a3eaec40e8cd75d2f48741edd49329ed8941cd2b8bca8df4f8ab80f64098efa" } } ], "extra": [ 1, 2, 212, 166, 217, 204, 245, 238, 11, 219, 168, 173, 248, 120, 150, 39, 143, 94, 12, 37, 225, 203, 72, 56, 24, 207, 14, 236, 210, 102, 149, 8, 215, 2, 17, 0, 0, 0, 1, 100, 15, 244, 143, 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