Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e2625e4b5f187d96991704ed7fd7cd1d4e9cd7071a0a883309b20184a4f3b4

Tx prefix hash: 3e2f2112f1906884cafddfe94c20256101a1a07880b9fab36448324fd654c298
Tx public key: e6f3528090041d7d37975c560fa5e3408676e423b0a7312ef956d2a124b38ee1
Timestamp: 1579188704 Timestamp [UCT]: 2020-01-16 15:31:44 Age [y:d:h:m:s]: 04:346:01:35:37
Block: 46911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136801 RingCT/type: yes/0
Extra: 01e6f3528090041d7d37975c560fa5e3408676e423b0a7312ef956d2a124b38ee10211000000024943cd9f000000000000000000

1 output(s) for total of 429.106626132000 dcy

stealth address amount amount idx
00: 88fe076731e10dd067c63020d7b0732d8db174d92caafdb57e4d91465684a93c 429.106626132000 86525 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": 46921, "vin": [ { "gen": { "height": 46911 } } ], "vout": [ { "amount": 429106626132, "target": { "key": "88fe076731e10dd067c63020d7b0732d8db174d92caafdb57e4d91465684a93c" } } ], "extra": [ 1, 230, 243, 82, 128, 144, 4, 29, 125, 55, 151, 92, 86, 15, 165, 227, 64, 134, 118, 228, 35, 176, 167, 49, 46, 249, 86, 210, 161, 36, 179, 142, 225, 2, 17, 0, 0, 0, 2, 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