Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9482f4244f84702d0a2a05b339336930f237f2b5371ee21852f36d23482177f

Tx prefix hash: acebc3f24d0a4719095a52a5dcf1018bd07a5caeb113ec8ccc8d4ca663136b45
Tx public key: 05a348c140cb8e5cc784eb07eafe683c8c002e01041e2060db431b2c803d308c
Timestamp: 1583931276 Timestamp [UCT]: 2020-03-11 12:54:36 Age [y:d:h:m:s]: 04:260:21:31:40
Block: 80395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081654 RingCT/type: yes/0
Extra: 0105a348c140cb8e5cc784eb07eafe683c8c002e01041e2060db431b2c803d308c02110000000a203e3db0000000000000000000

1 output(s) for total of 332.367676316000 dcy

stealth address amount amount idx
00: 4c4df9abd173d639ecb5f47f9f8bb46e4fbe76a1fa5c340bfcbf12493403cc51 332.367676316000 147163 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": 80405, "vin": [ { "gen": { "height": 80395 } } ], "vout": [ { "amount": 332367676316, "target": { "key": "4c4df9abd173d639ecb5f47f9f8bb46e4fbe76a1fa5c340bfcbf12493403cc51" } } ], "extra": [ 1, 5, 163, 72, 193, 64, 203, 142, 92, 199, 132, 235, 7, 234, 254, 104, 60, 140, 0, 46, 1, 4, 30, 32, 96, 219, 67, 27, 44, 128, 61, 48, 140, 2, 17, 0, 0, 0, 10, 32, 62, 61, 176, 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