Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb832042ace3dd1fdee44fb202369cd4e74c3b15da0d6efefceee18532baf73

Tx prefix hash: 99ff4fc86107eb55ad5dbd9cdc256030831ee7433c155423c11909da69b5af4a
Tx public key: 45e5bdb7e889432f32eb803d3e7adb02709349f2d1b855fecc868c4a6633ed2a
Timestamp: 1581466806 Timestamp [UCT]: 2020-02-12 00:20:06 Age [y:d:h:m:s]: 04:322:06:24:04
Block: 63027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122520 RingCT/type: yes/0
Extra: 0145e5bdb7e889432f32eb803d3e7adb02709349f2d1b855fecc868c4a6633ed2a021100000002d81c26c0000000000000000000

1 output(s) for total of 379.460171921000 dcy

stealth address amount amount idx
00: c18f22fcf12a93d0e237063c0b7e72e72757f22cbda7d9367e08941214cb9743 379.460171921000 116228 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": 63037, "vin": [ { "gen": { "height": 63027 } } ], "vout": [ { "amount": 379460171921, "target": { "key": "c18f22fcf12a93d0e237063c0b7e72e72757f22cbda7d9367e08941214cb9743" } } ], "extra": [ 1, 69, 229, 189, 183, 232, 137, 67, 47, 50, 235, 128, 61, 62, 122, 219, 2, 112, 147, 73, 242, 209, 184, 85, 254, 204, 134, 140, 74, 102, 51, 237, 42, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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