Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66bd87d5471db07e451f08c611a8d43ac63b4f8f91d56135d961b9c01e6a01d5

Tx prefix hash: df34414a3ab8b6187af135e6e732a2f9d6942faa0c8ee63c7326d4d44e2dc83c
Tx public key: e0aedd71fa85595fdd9a8545025e6ae349060bde7e77b44108217d895588390b
Timestamp: 1635962924 Timestamp [UCT]: 2021-11-03 18:08:44 Age [y:d:h:m:s]: 03:362:05:55:14
Block: 366637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1034924 RingCT/type: yes/0
Extra: 01e0aedd71fa85595fdd9a8545025e6ae349060bde7e77b44108217d895588390b02110000000c745f00f8000000000000000000

1 output(s) for total of 37.426552112000 dcy

stealth address amount amount idx
00: 4cccde65e3e00dfa3359071e3d375afb99910ee6c3a45644de27c79a381db818 37.426552112000 744179 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": 366647, "vin": [ { "gen": { "height": 366637 } } ], "vout": [ { "amount": 37426552112, "target": { "key": "4cccde65e3e00dfa3359071e3d375afb99910ee6c3a45644de27c79a381db818" } } ], "extra": [ 1, 224, 174, 221, 113, 250, 133, 89, 95, 221, 154, 133, 69, 2, 94, 106, 227, 73, 6, 11, 222, 126, 119, 180, 65, 8, 33, 125, 137, 85, 136, 57, 11, 2, 17, 0, 0, 0, 12, 116, 95, 0, 248, 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