Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b13580a4ee79087dd2b58b72d4e92b2b579a5c8e25258114b9eb5832e29beb

Tx prefix hash: 50c68f11e276153edbf08cc64c68c91b8cb8326a05630ea956b6874d00afbb4b
Tx public key: 35a0abad8908f47d2c782b9518dbf902624dd07d0dde491a368de1a8ac117e6d
Timestamp: 1648477644 Timestamp [UCT]: 2022-03-28 14:27:24 Age [y:d:h:m:s]: 03:217:14:40:45
Block: 468250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933465 RingCT/type: yes/0
Extra: 0135a0abad8908f47d2c782b9518dbf902624dd07d0dde491a368de1a8ac117e6d0211000000024da16a3a000000000000000000

1 output(s) for total of 17.238267757000 dcy

stealth address amount amount idx
00: 0fa6f5af9c9876d0f18b29b8e3a9b79702438081675dd3522a75be8442513b0c 17.238267757000 886934 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": 468260, "vin": [ { "gen": { "height": 468250 } } ], "vout": [ { "amount": 17238267757, "target": { "key": "0fa6f5af9c9876d0f18b29b8e3a9b79702438081675dd3522a75be8442513b0c" } } ], "extra": [ 1, 53, 160, 171, 173, 137, 8, 244, 125, 44, 120, 43, 149, 24, 219, 249, 2, 98, 77, 208, 125, 13, 222, 73, 26, 54, 141, 225, 168, 172, 17, 126, 109, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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