Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d31982b9cde6d6ef8d7cbd636c115a0c4747149c5e1d20d0dac6ba598298730

Tx prefix hash: e864f5169f422f83afcf84e15b1c37124b9ad1a1aff6419fc16628825fea95da
Tx public key: 3001686085c7c8c65e0ef862d5f4808c479ac8e719f87017e49808eba1b8924f
Timestamp: 1582922614 Timestamp [UCT]: 2020-02-28 20:43:34 Age [y:d:h:m:s]: 04:262:11:08:31
Block: 73607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081224 RingCT/type: yes/0
Extra: 013001686085c7c8c65e0ef862d5f4808c479ac8e719f87017e49808eba1b8924f0211000000044ac5aa02000000000000000000

1 output(s) for total of 350.034017479000 dcy

stealth address amount amount idx
00: be34f46a06fb61ea434d9e08c5bad2668b907a8d02d8d59aec78605a5cbbe390 350.034017479000 135829 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": 73617, "vin": [ { "gen": { "height": 73607 } } ], "vout": [ { "amount": 350034017479, "target": { "key": "be34f46a06fb61ea434d9e08c5bad2668b907a8d02d8d59aec78605a5cbbe390" } } ], "extra": [ 1, 48, 1, 104, 96, 133, 199, 200, 198, 94, 14, 248, 98, 213, 244, 128, 140, 71, 154, 200, 231, 25, 248, 112, 23, 228, 152, 8, 235, 161, 184, 146, 79, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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