Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1616a97b9dd4a0ff40ae2e6ae461394ad54c9ded55b4dba8d8c934d8c0b0ec

Tx prefix hash: 20f6827b241c0f087f6b947df7c4488378179573735a47cf744a7f7658ea6656
Tx public key: 0eed7708c146167f4293b57ee7993568ef10b16642429aeee1f3b7e5353c4644
Timestamp: 1581242091 Timestamp [UCT]: 2020-02-09 09:54:51 Age [y:d:h:m:s]: 04:282:00:44:33
Block: 61185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093727 RingCT/type: yes/0
Extra: 010eed7708c146167f4293b57ee7993568ef10b16642429aeee1f3b7e5353c464402110000001a4943cd9f000000000000000000

1 output(s) for total of 384.830524334000 dcy

stealth address amount amount idx
00: 4b3ed10ef04d112c849ba74ef00d0dc40db02aef43298273e72192a7fc6acb21 384.830524334000 112753 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": 61195, "vin": [ { "gen": { "height": 61185 } } ], "vout": [ { "amount": 384830524334, "target": { "key": "4b3ed10ef04d112c849ba74ef00d0dc40db02aef43298273e72192a7fc6acb21" } } ], "extra": [ 1, 14, 237, 119, 8, 193, 70, 22, 127, 66, 147, 181, 126, 231, 153, 53, 104, 239, 16, 177, 102, 66, 66, 154, 238, 225, 243, 183, 229, 53, 60, 70, 68, 2, 17, 0, 0, 0, 26, 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