Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10c353495e25bec1c2c6d4687593e85e1af01f2b02f37ee483a7fcbe5585dbc1

Tx prefix hash: 3dd033a764dcb9e95685657311fada34174e27cfa2266cbe0c0cfe1798e82c7b
Tx public key: cdf1e37697c465eedd0ee1936be5757bca9a8d1bc7002e23a3f7df2b68362851
Timestamp: 1578076598 Timestamp [UCT]: 2020-01-03 18:36:38 Age [y:d:h:m:s]: 05:107:13:15:43
Block: 37904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226813 RingCT/type: yes/0
Extra: 01cdf1e37697c465eedd0ee1936be5757bca9a8d1bc7002e23a3f7df2b683628510211000000034943cd9f000000000000000000

1 output(s) for total of 459.630843189000 dcy

stealth address amount amount idx
00: d1bfda66c982f8c7e7812d39b816bd644f17cea02be20df60d1bb90aeafde6f9 459.630843189000 64449 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": 37914, "vin": [ { "gen": { "height": 37904 } } ], "vout": [ { "amount": 459630843189, "target": { "key": "d1bfda66c982f8c7e7812d39b816bd644f17cea02be20df60d1bb90aeafde6f9" } } ], "extra": [ 1, 205, 241, 227, 118, 151, 196, 101, 238, 221, 14, 225, 147, 107, 229, 117, 123, 202, 154, 141, 27, 199, 0, 46, 35, 163, 247, 223, 43, 104, 54, 40, 81, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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